Fix assertoor workflow: bump setup-python to v6#10645
Merged
LukaszRozmej merged 2 commits intomasterfrom Mar 10, 2026
Merged
Conversation
The v6.1.1 tag does not exist in actions/setup-python, causing the assertoor test workflow to fail on every master push. This changes to the v6 major version tag matching the pattern used in other workflows.
rubo
approved these changes
Feb 25, 2026
LukaszRozmej
approved these changes
Mar 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
actions/setup-python@v6.1.1tag does not exist, causing every assertoor run to fail at the "Set up Python" stepactions/setup-python@v6, matching the pattern used insync-supported-chains.ymlVerification
big-calldata-tx-test) is a pre-existing issue unrelated to this fixTest plan
test-assertoor.ymlon branch, confirmed Python setup succeeds